Skip to content

Conversation

@stevhliu
Copy link
Member

Refreshes the AutoPipeline docs with a clearer explanation of how its different from DiffusionPipeline.

@HuggingFaceDocBuilderDev

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.

@stevhliu stevhliu requested a review from sayakpaul August 15, 2025 21:16
@sayakpaul sayakpaul requested a review from yiyixuxu August 16, 2025 02:16
Copy link
Collaborator

@yiyixuxu yiyixuxu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thanks @stevhliu !
I left one comment

# AutoPipeline

Diffusers provides many pipelines for basic tasks like generating images, videos, audio, and inpainting. On top of these, there are specialized pipelines for adapters and features like upscaling, super-resolution, and more. Different pipeline classes can even use the same checkpoint because they share the same pretrained model! With so many different pipelines, it can be overwhelming to know which pipeline class to use.
[AutoPipeline](../api/models/auto_model) is a *task-first* pipeline that automatically selects the correct pipeline subclass based on the task. It handles the complexity of loading different pipeline subclasses without needing to know the specific pipeline subclass name.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

oh I think AutoPipelline select based on task & model; DiffusionPipeline only based on model. So AutoPipeline take just one step further, here it sounds like they are two parallel approach

so basically for DiffusionPipeline

model -> pipeline subclass 

for Auto

model -> pipeline subclass ->pipeline subclass within the same pipeline group for a different task

Copy link
Member

@sayakpaul sayakpaul left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks! Don't know how it got missed. Sorry for the delay.

Comment on lines 51 to 52
[AutoPipeline](../api/models/auto_model) supports [StableDiffusion](../api/pipelines/stable_diffusion/overview), [Stable Diffusion XL](../api/pipelines/stable_diffusion/stable_diffusion_xl), [ControlNet](../api/pipelines/controlnet), [Kandinsky 2.1](../api/pipelines/kandinsky.md), [Kandinsky 2.2](../api/pipelines/kandinsky_v22), and [DeepFloyd IF](../api/pipelines/deepfloyd_if).

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is Flux not supported? 👀 Maybe we could open it up to the community to add some of the recent models. Cc: @yiyixuxu

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

My bad, Flux is supported! I just added a note with a link to check the mappings since the list might become quite long if we listed all the supported models.

"
```

You can learn more about the [`~DiffusionPipeline.from_pipe`] method in the [Reuse a pipeline](../using-diffusers/loading#reuse-a-pipeline) guide.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The from_pipe note seems important. Do we want to remove it?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it's ok not to have it here since we're not showing any code examples that demonstrate using from_pipe, so its a bit out of scope.

@stevhliu stevhliu merged commit 6549b04 into huggingface:main Sep 3, 2025
1 check passed
@stevhliu stevhliu deleted the autopipeline branch September 3, 2025 04:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants